Hi Tim,

I am using SkyDemon for some time now and I am happy with it.

I have a suggestion regarding the Flight Plans - everytime I plan a trip (which I do always well in advance of the actual flying) I try to get everything ready and save the trip to be able to recall it later. I would appreciate if SD had a funcionality which would allow it to prepare a Flight Plan (fill in all the details about the aircraft, route, times etc) and save it togehter with all other trip data (as a part of the package).

At the moment, once I fill in the Flight Plan I can either file it or cancel it.

I'd like to be able to recall the prepared Flight Plan to update some details before the flight or once all the remaining details are known and file it (now I have to fill in everything from scratch).

What do you think about it?

Thanks,

Milan

I like the idea, but it would take a bit of effort to implement and we're quite busy on other features at the moment. Perhaps more people will contribute to this thread to indicate whether they like it.

Yes, I like the idea of a "store" option as well so flight can be prepared early then implemented later.

Nice idea.

Yes I like the idea too.

I would use this feature.

and me.



Ian

Moi aussi



Al

So, next to the "Submit Plan" button there could be another button called "Save for Later" or similar. This could then do one of two things:

a) save the flightplan to the customer area, so that it could be filed at the click of a button later from any browser, in the same way that you can cancel/close flightplans now. The plan would not be re-loadable for editing in Plan/Web.

b) save the flightplan to disk, so that it could be reloaded back into Plan/Web and then filed later from there.

Which sounds preferable and why?

I think both work equally well for different people!



a) would be great for someone who doesn't carry their laptop with them - you could stroll up to any computer at your destination and file your return flight plan.



b) would be great for anyone who does carry their computer with them



Given that a) would work universally, and b) excludes some users, logic suggests that if you were to implement only one option, it should be a)?



Having said that, if you can't edit the flight plan before resubmitting it, then a) may be of limited utility.



So you need to do both

I think a flightplan 'save' feature must have the ability to be edited before submitting, that's really the whole point i.e do some work up front and then fine tune and submit when you're 'green for go'.



Ian